Events - 1.46.0

Selecting the check box will show special days in the past.

No other changes to special days have been made

For example, if you have imported Reservations bookings to Events, and all those bookings have been mapped to a single temporary menu for importing purposes, then you manually change that temporary menu to a proper Events menu on each booking, provided that you create a booking rule triggered by the above Events menu, then the menu change will result in booking requirements updating to respect the menu booking rule.

This check for a higher priority booking rule and automatic requirement update will be triggered in Events Host App, Tables Host App and liveRes External API.

All references to multiple areas have now been removed.

It is now possible to select only one area per capacity group.

No other changes to area capacity groups have been made

 

No changes have been made to how the pre-auth action works.

• A Host changes the deposit amount or a deposit due date.

• A Host changes a pre-order due date.

• A Host adds a deposit and/or pre-order requirement on a booking where they were not previously required.

• A Host removes a deposit and/or a pre-order requirement from a booking.

• A menu is changed on an existing booking and this change results in matching to another booking rule and thus automatic requirement update to respect the new booking rule.

This email will notify an event organiser when booking requirements have been updated so that they are aware of the change and have a chance to satisfy the booking requirements on time.

As any other existing email template, the new ‘Requirement Updated’ template can be found at Events Admin App > Emails > Customer emails.

The default template content is as follows:

Dear %GuestFirstName%,

There is a change in requirements for your %OccasionName% at %BookingTime% on %BookingDate% for %TotalCovers% people.

You can view the details here.

Estate Admin can edit the template as per existing functionality.

Currently Events sends deposit paid to Tables only when that event has a deposit requirement against it. Events will now send the total payment sum to Tables, including any overpayment.

Changes to tables are as follows:

• In the Tables host app, the yellow pill to display the total sum of payments,

• In Tables host app, a new orange pill to display total paid/total required with the same symbol as events and the same hover over text as events,

• In Tables host app, guest details also show the orange pill if an overpayment exists,

• Orange pill will only show if an overpayment exists.

  You can view an example below:

  

  

The code related to Aztec sync hasn't changed however, with events passing overpayments to Tables, Tables will now pass overpayments to Aztec. (Reservations already does this)